<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>
 <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
 <meta http-equiv="Content-Language" content="en-gb" />
 <meta name="MSSmartTagsPreventParsing" content="true" />
 <meta http-equiv="imagetoolbar" content="false" />
 <meta name="Copyright"
  content="Design and contents Copyright (c) 2009 Richard Boulton" />
 <meta name="keywords"
  content="Python, Web API, REST, WSGI, framework, open-source" />
 <meta name="description"
  content="WSGIWAPI is a framework for building WSGI applications providing web APIs" />

 <title>WSGIWAPI | Quick and easy web APIs</title>

 <link rel="stylesheet" type="text/css" href="media/homepage.css" media="screen" />
</head>

<body id="homepage" class="default">
 <div class="contentbox">
  <h1>WSGIWAPI</h1>
  <p>

   WSGIWAPI makes it easy to build web APIs in Python.  You simply define a
   hierarchical tree of URI components, with callables as the leaves of the
   tree, and WSGIWAPI does the work of making this into a WSGI application.

  </p>
  <p>

   The clever bit is that you don't need to know anything about WSGI, or the
   details of HTTP.  You just define the callables and the URI components, and
   obtain a generic application object that lots of web servers can talk to.
   There's even a built-in web server so for simple setups you don't need to
   configure anything.

  </p>
  <p>

   WSGIWAPI also provides some additional features, such as
   automatic documentation support for your API and parameter
   validation.
   
  </p>
  <h2>Documentation</h2>
  <ul>
   <li><a href="docs/HEAD">development version</a></li>
   <li><a href="docs/0.3.1">0.3.1 release</a></li>
   <li><a href="docs/0.3">0.3 release</a></li>
   <li><a href="docs/0.2">0.2 release</a></li>
   <li><a href="docs/0.1.1">0.1.1 release</a></li>
   <li><a href="docs/0.1">0.1 release</a></li>
  </ul>

  <h2>Download</h2>
  <ul>
   <li><a href="http://wsgiwapi.googlecode.com/files/WSGIWAPI-0.3.1.tar.gz">WSGIWAPI-0.3.1.tar.gz</a></li>
   <li><a href="http://wsgiwapi.googlecode.com/files/WSGIWAPI-0.3.tar.gz">WSGIWAPI-0.3.tar.gz</a></li>
   <li><a href="http://wsgiwapi.googlecode.com/files/WSGIWAPI-0.2.tar.gz">WSGIWAPI-0.2.tar.gz</a></li>
  </ul>

  <small>
    Older releases were made under the name WSGIWebAPI.
    <ul>
     <li><a href="http://wsgiwapi.googlecode.com/files/WSGIWebAPI-0.1.1.tar.gz">WSGIWebAPI-0.1.1.tar.gz</a></li>
     <li><a href="http://wsgiwapi.googlecode.com/files/WSGIWebAPI-0.1.tar.gz">WSGIWebAPI-0.1.tar.gz</a></li>
    </ul>
  </small>

  <h2>Development</h2>
  <p>

   WSGIWAPI has a <a href="http://code.google.com/p/wsgiwapi/">project page at google code</a>.  Go here for:

  </p>
  <ul>
   <li><a href="http://code.google.com/p/wsgiwapi/issues/list">Issue tracker</a></li>
   <li><a href="http://code.google.com/p/wsgiwapi/source/checkout">Subversion repository</a></li>
  </ul>

  <h2>Author</h2>
  <p>
   WSGIWAPI was written by Richard Boulton.
  </p>
 </div>
</body>
</html>
